for whatever reason, the CI machine isn't dropping the port that NodeJS uses as part of its compile process. It's a randomly selected port and I can't find anywhere in the upstream that where it's getting invoked. Conversations with upstream maintainers suggest this is a dependency throwing the problem that is out of their hands. Open to any and all suggestions.

for whatever reason, the CI machine isn't dropping the port that NodeJS uses as part of its compile process. It's a randomly selected port and I can't find anywhere in the upstream that where it's getting invoked. Conversations with upstream maintainers suggest this is a dependency throwing the problem that is out of their hands. Open to any and all suggestions.

once again, the port builds fine locally on multiple machines.

Seems similar to louislam/dockge#353 but the workaround used there doesn't seem applicable, since there doesn't seem to be an existing socket anywhere on the system when the port build starts.

Guess we'll see how that goes on the buildbot.

Guess we'll see how that goes on the buildbot.

seems to be fine? https://build.macports.org/builders/ports-14_arm64-builder/builds/56893